2017-06-14 - 40801 - Spec - Check feasibility of changing existing table to an existing characteristic in COPA #FISD #COPA #US
SPECIFICATIONS
40801 - Spec - Check feasibility of changing existing table to an existing characteristic in COPA
Purpose
Check feasibility of changing existing table to an existing characteristic in COPA.
Admin Info
Purpose
|
Check feasibility of changing existing table to an existing characteristic in COPA
|
Requested By
|
Matthew Bolles
|
Spec Created By
|
Surya Basa
|
Spec Created Date
|
07/05/2017
|
Spec QA by
|
Surya Basa
|
Objects
|
|
Document Status
|
Complete
|
Estimates
Sl.No
|
Activity
|
Estimation in Hours
|
1
|
Research
|
|
2
|
Documentation
|
|
3
|
Development/ Config
|
|
4
|
Unit test in DEV
|
|
5
|
Unit test in QUA
|
|
6
|
Other activity
|
|
|
TOTAL
|
|
References
Prior Tickets
[Provide links of prior associated Spec / Break Fix BOSS document(s)]
Documents
[Attach any document(s) received for the requirement(s)]
Spec Changes
[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]
Sl.
|
Change Details
|
Requested By
|
Requested On
|
Notes if any
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Functional Requirement
Purpose/WHY:
[Explain the purpose of the project and the reason why this requirement has come]
The sales group VKGRP and sales office VKBUR should be picked from VBAK for COPA postings rather than KNVV as mapped currently.
From what I understand it's more from the BI perspective. Let me outline the problem more in detail.
Currently, the business runs reports that pull information from COPA. The information is meant for them to be able to view the amount of sales that our sales reps have.
The problem is that COPA doesn't update until orders are invoiced I believe. So, this has been resulting in sales being assigned to the wrong sales rep.
The sales rep who placed the sales order (which should be stored in the sales header-VBAK) is sometimes different than the rep who is currently serving that customer and therefore stored in the customer master when the data is pulled form COPA to run the reports.
COPA currently pulls sales rep and sales manager from the customer master table (KNVV). But it needs to pull from the sales header table (VBAK) in order to show the correct sales rep associated with orders.
Brief example:
Sales Rep John places an order for $10,000 with Customer XYZ on 6/1/2017 Sales Rep Samantha gets assigned to Customer XYZ on 6/5/2017.
The order for $10,000 is invoiced on 6/10/2017.
As a result of this, in COPA, Sales rep Samantha would show as the sales rep for that order instead of Sales Rep John.
All we need is to change the mapping in COPA for sales rep and sales manager to point at VBAK instead of KNVV.
In Scope:
[List the
activities to be included in scope]
Out of Scope:
[Out of scope activities]
Solution Summary
[Discuss this section with Requester and get approval prior to beginning work]
BW
This can be accomplished on the BW end with minor code changes for Sales Rep and Sales Manager lookup, listed on the Sales order. There are two possibilities here:
1. With BW COPA source reload - Once the changes are moved into BW Production, we need to refresh the COPA source completely. This will ensure that historical data is also updated with correct Sales Rep and Sales Manager values. This will require a downtime of approx 8-10 hours during which this source will be unavailable for reporting. The total effort is approx 16-20 Hours including development, testing, transports and data reload but excluding any report level changes.
2. Without BW COPA source reload - Once the changes are moved into BW Production, the data posted henceforth will have correct Sales Rep and Sales Manager values. All the historical data will have blank values. This will not require a downtime and the total effort is approx 16-20 Hours including development, testing and transports but excluding any report level changes.
Config
New characteristics have been defined for sales office and sales group, source being VBAK but they cannot be used in the same operating concern (e.g., COPA table CE10010) as the data elements (VKGRP and VKBUR) are the same though the source tables are different (VBAK and KNVV).
In such a scenario, in order to replace the existing characteristics, we’d need to re-organize the COPA table and follow procedural steps to achieve this. The following are few of the implications –
- 1. This has to be done in individual environments as the changes are not transportable.
- 2. During the process the table is not available. Hence, transactions and reporting can’t be carried out.
- 3. It is required to take a backup of the COPA table as it involves regeneration of the table with new characteristics.
Further, please refer OSS 21207 for details. Though our version is not part of the note but the implications could be the same as I couldn’t find any other relevant notes for this change.
I’d suggest raising an OSS with SAP to handle this requirement following the best practices.
Test Plan
[List test scenarios/cases to be executed here]
Test ID
|
Test Scenario
|
Expected Results
|
SD001
|
|
|
SD002
|
|
|
Solution Details
[Provide complete technical details for configuration or programming here]
The requirement was handled in BW by choosing option 1.
Issues
[List Issues / Bugs identified in configuration or development]